Light electric vehicle defect management

ABSTRACT

The present disclosure describes a system for detecting, identifying and addressing a maintenance event for light electric vehicles. The maintenance event may be detected based on rider profile information, riding parameter information and light electric vehicle information. If a maintenance event is detected, a light electric vehicle management system may determine an action that addresses the maintenance event and provide instructions regarding the action to the light electric vehicle and/or one or more individuals that are trained or otherwise certified to address the maintenance event.

CROSS-REFERENCE TO RELATED APPLICATION

This application claims priority to U.S. Provisional Application No.62/925,134 titled Light Electric Vehicle Defect Management, filed onOct. 23, 2019, the entire disclosure of which is hereby incorporated byreference in its entirety.

BACKGROUND

Electric vehicles, such as electric scooters and electric bicycles, aretypically available for individuals to reserve and ride for a period oftime. However, overtime, these electric vehicles may need to beserviced.

SUMMARY

The present disclosure describes methods and systems for detecting amaintenance event for light electric vehicles. As will be explained ingreater detail below, the maintenance event may be detected in a numberof different ways. For example, various sensors on or otherwiseassociated with the light electric vehicle may gather information aboutone or more performance metrics of the light electric vehicle. Theinformation may then be provided to a light electric vehicle managementsystem that determines, based on the sensor information, whether amaintenance event is occurring and how the maintenance event can beaddressed. In some examples, rider habit information, either alone or incombination with the sensor information, may also be used to detect amaintenance event.

Accordingly, the present disclosure describes a computer-implementedmethod for detecting a maintenance event. In some examples, the methodmay be performed by a light electric vehicle management system. Forexample, the light electric vehicle management system may receive lightelectric vehicle information from one or more sensors associated with alight electric vehicle. When the light electric vehicle information isreceived, the light electric vehicle management system uses the lightelectric vehicle information to detect a maintenance event associatedwith the light electric vehicle. The light electric vehicle managementsystem then determines an action that addresses the maintenance event.The light electric vehicle management system may also determine, basedat least in part, on profile information of an individual that is ridingor using the light electric vehicle, that the individual can perform theaction. In response to determining that the individual can perform theaction, the light electric vehicle management system generates anotification that provides information about how the maintenance eventcan be addressed. The light electric vehicle management system may thensend the notification to a computing device associated with theindividual.

The present disclosure also describes a system having at least oneprocessor and a memory coupled to the at least one processor. The memorystores instructions that, when executed by the at least one processor,causes the at least one processor to perform operations. Theseoperations comprise receiving light electric vehicle information fromone or more sensors associated with a light electric vehicle. The lightelectric vehicle information is used to detect a maintenance eventassociated with the light electric vehicle. When the maintenance eventis detected, an anticipated destination of the light electric vehicle isdetermined. The anticipated destination is based, at least in part, onrider profile information associated with an individual that is riding,has reserved or is otherwise using the light electric vehicle. When theanticipated destination is determined, one or more individuals that areassociated with the anticipated destination and that are qualified toperform an action that addresses the maintenance event are identified. Anotification may then be provided to a computing device associated withat least one of the one or more individuals. The notification mayinclude a request that the at least one of the one or more individualsperform the action on the light electric vehicle when the light electricvehicle reaches the anticipated destination.

The present disclosure also describes a computer-implemented method fordetecting a maintenance event. This method may be performed by a lightelectric vehicle management system. For example, the light electricvehicle management system may receive light electric vehicle conditioninformation from a light electric vehicle. The light electric vehicleinformation may indicate a maintenance event. The light electric vehiclemanagement system may determine a current location of the light electricvehicle. When a riding request is received, the light electric vehiclemanagement system may determine whether the individual that submittedthe request is associated with the current location of the lightelectric vehicle. The light electric vehicle management system may alsodetermine based, at least in part, on profile information associatedwith the individual, whether the individual has training to perform anaction to remedy or otherwise address the maintenance event. When thelight electric vehicle management system determines the individual istrained to perform the action, a notification is provided to a computingdevice associated with the individual. The notification may include thecurrent location of the light electric vehicle and the action to beperformed on the light electric vehicle.

Also described is a computer-implemented method for detecting amaintenance event. In some examples, this method may be performed by alight electric vehicle management system. For example, the lightelectric vehicle management system may receive, in real-time orsubstantially real-time, a riding parameter associated with a rider of alight electric vehicle. The riding parameter may then be compared to aset of previously received and/or stored riding parameters. When thecomparison of the riding parameters indicates the riding parameter isbelow an efficiency threshold, the light electric vehicle managementsystem may request sensor information from one or more sensorsassociated with the light electric vehicle. The light electric vehiclemanagement system may then determine based, at least in part, on thesensor information, whether the riding parameter being below theefficiency threshold is caused, at least in part, by a maintenance eventassociated with the light electric vehicle or a condition of the rider.When it is determined the riding parameter is below the efficiencythreshold due to the maintenance event, the light electric vehiclemanagement system provides a maintenance notification to the lightelectric vehicle and/or to a computing device associated with the rider.

The present disclosure also describes a computer-implemented method foraddressing a detected maintenance event. In some examples, this methodmay be performed by a light electric vehicle management system. Forexample, the light electric vehicle management system may receive ariding parameter associated with a rider of a light electric vehicle andmay also obtain a set of previously received riding parametersassociated with the rider. The light electric vehicle management systemmay also determine that the riding parameter is below a riding parameterthreshold associated with the rider based, at least in part, on acomparison of the riding parameter to the set of previously receivedriding parameters associated with the rider. In response to determiningthat the riding parameter is below the riding parameter threshold, thelight electric vehicle management system may request sensor informationfrom one or more sensors associated with the light electric vehicle. Thelight electric vehicle management system may also determine, based atleast in part, on the sensor information, whether the riding parameterbeing below the riding parameter threshold is caused, at least in part,by a maintenance event associated with the light electric vehicle. Thesensor information may be analyzed to determine whether the maintenanceevent is addressable by a set of instructions provided to the lightelectric vehicle. The set of instructions may be used to modify one ormore operating parameters of the light electric vehicle. When it isdetermined that the maintenance event is addressable by the set ofinstructions, the light electric vehicle management system provides theset of instructions to the light electric vehicle.

Also described is a method for matching riders with light electricvehicles based, at least in part, on performance metrics of the lightelectric vehicle and on riding habits of the requesting rider. Themethod may be performed by a light electric vehicle management system.For example, the light electric vehicle management system may receive alight electric vehicle riding request from a computing device associatedwith an individual. The light electric vehicle management system mayidentify a stored rider profile associated with the individual anddetermine, based at least in part, on the rider profile, a ridingbehavior of the individual. The light electric vehicle management systemmay also determine a location of the individual and identify one or morelight electric vehicles associated with the location of the rider. Thelight electric vehicle management system may also determine, based atleast in part, on sensor information received from each of the one ormore light electric vehicles, a performance metric of each of the one ormore electric vehicles. The light electric vehicle management system mayalso compare the performance metric of each of the one or more lightelectric vehicles to the riding behavior of the individual and select atleast one of the one or more light electric vehicles for the individualbased, at least in part, on the comparison of the performance metric andthe riding behavior. The light electric vehicle management system maythen provide a location of the selected light electric vehicle to thecomputing device associated with the individual.

BRIEF DESCRIPTION OF THE DRAWINGS

Non-limiting and non-exhaustive examples are described with reference tothe following Figures.

FIG. 1 illustrates a light electric vehicle ridesharing system accordingto an example.

FIG. 2A illustrates a light electric vehicle management system fordetecting a maintenance event for a light electric vehicle according toan example.

FIG. 2B illustrates the light electric vehicle management system of FIG.2A sending instructions that address the maintenance event to one ormore computing devices and/or to one or more light electric vehiclesaccording to an example.

FIG. 3A illustrates a light electric vehicle management system fordetecting a maintenance event for a light electric vehicle according toanother example.

FIG. 3B illustrates the light electric vehicle management system of FIG.3A sending instructions that address the maintenance event to one ormore computing devices according to an example.

FIG. 4 illustrates an example user interface of a computing device, theexample user interface showing instructions for addressing a detectedmaintenance event according to an example.

FIG. 5A illustrates an example user interface that shows a location ofone or more light electric vehicles according to an example.

FIG. 5B illustrates the example user interface of FIG. 5A in which thelocation of one of the light electric vehicles has been removedaccording to an example.

FIG. 6 illustrates a method for matching an individual with a lightelectric vehicle using a determined riding behavior of the individualand one or more performance metrics of a light electric vehicleaccording to an example.

FIG. 7 illustrates a method for detecting and addressing a maintenanceevent of a light electric vehicle according to an example.

FIG. 8 illustrates another method for detecting and addressing amaintenance event of a light electric vehicle according to an example.

FIG. 9 illustrates a method for detecting a maintenance event of a lightelectric vehicle and providing a notification of the maintenance eventto a computing device associated with an individual and/or a computingdevice associated with the light electric vehicle according to anexample.

FIG. 10 illustrates a method for detecting and addressing a maintenanceevent of a light electric vehicle according to an example.

FIG. 11 illustrates a computing device that may be used by the lightelectric vehicles and/or systems described herein.

DETAILED DESCRIPTION

In the following detailed description, references are made to theaccompanying drawings that form a part hereof, and in which are shown byway of illustrations specific embodiments or examples. These aspects maybe combined, other aspects may be utilized, and structural changes maybe made without departing from the present disclosure. Examples may bepracticed as methods, systems or devices. Accordingly, examples may takethe form of a hardware implementation, an entirely softwareimplementation, or an implementation combining software and hardwareaspects. The following detailed description is therefore not to be takenin a limiting sense, and the scope of the present disclosure is definedby the appended claims and their equivalents.

Electric ridesharing vehicles, such as electric assist bicycles andelectric scooters (also referred to herein as “electric vehicles” or“light electric vehicles”), are typically made available for individualsto reserve for a period of time. For example, in some examples, anindividual may access an application executing on a mobile phone orother computing device and determine a location of one or more lightelectric vehicles within their vicinity. Once a particular lightelectric vehicle is located, the individual may reserve that particularlight electric vehicle using the application. The individual may thenproceed to the location of the light electric vehicle, activate thelight electric vehicle and begin using the light electric vehicle. Whenthe individual has reached her desired location, the individual may endtheir use of the light electric vehicle using the application. The lightelectric vehicle may then be subsequently reserved and/or used byanother individual.

Because these light electric vehicles are available for use on publicroads and are often parked outside, the light electric vehicles may beexposed to various environmental conditions such as rain, snow, sun, andso on. Over time, continuous exposure to these elements may damage thelight electric vehicles. Additionally, as each of the light electricvehicles are used by various riders, the light electric vehicles may besubject to wear and tear and/or be damaged—either intentionally (e.g.,vandalism) or unintentionally. Wear and tear and/or damage to the lightelectric vehicles may impact the overall performance of the lightelectric vehicles and as a result, could negatively impact the ridingexperience of a current rider and/or a subsequent rider.

As such, the present disclosure describes a light electric vehiclemanagement system that determines, based on received light electricvehicle information from the light electric vehicle and/or rider profileinformation associated with a current rider, whether the light electricvehicle is operating below an operation threshold and/or whether variouscomponents of the light electric vehicle are operating as expected. Aswill be discussed in greater detail below, a light electric vehicle mayinclude one or more sensors can take readings and/or determine thestatus or functionality of different components, systems and/or parts ofthe light electric vehicle.

For example, the light electric vehicle may have a sensor thatdetermines the tire pressure of the light electric vehicle, a sensorthat detects an amount of torque that is being applied to one or morepedals of the light electric vehicle, a sensor that detect an amount oftraction provided by the tires of the light electric vehicle, and so on.In other examples, the information from the one or more sensors may beused to determine overall performance metrics of the light electricvehicle (e.g., battery usage rates, light electric vehicle speed, lightelectric vehicle acceleration, etc.). Using this information, the lightelectric vehicle management system may determine whether the lightelectric vehicle is experiencing or will experience a maintenance eventand should be serviced. Although specific sensors are mentioned, thelight electric vehicle may have any number of sensors that detect and/ordetermine a status of various components or parts of the light electricvehicle.

The light electric vehicle information gathered by the sensors may thenbe sent, via an application programming interface associated with thelight electric vehicle, to the light electric vehicle management system.The light electric vehicle management system uses the information todetect a maintenance event. As used herein, the term “maintenance event”means that information collected or received from the light electricvehicle indicates that the light electric vehicle is operating below anoperation threshold and as such, should be inspected, serviced and/orrepaired by an individual that has been trained to perform theinspection, service and/or repair. For example, a maintenance eventcould be an indication or other notification that the light electricvehicle should be serviced, needs to be serviced, and/or will need to beserviced within an indicated or anticipated amount of time. In someexamples, the information may indicate whether maintenance should beperformed on the light electric vehicle and/or the type of maintenancethat should be performed on the light electric vehicle. In otherexamples, the maintenance event may be addressed or fixed by one or moreinstructions provided by the light electric vehicle management system tothe light electric vehicle. When a computing device associated with thelight electric vehicle receives the instructions, the computing devicemay execute the instructions to address the maintenance event.

In some examples, the light electric vehicle information is collected inreal-time or substantially real time—even when the light electricvehicle is being ridden by an individual. Thus, when the light electricvehicle management system determines that the collected light electricvehicle information indicates a maintenance event, the light electricvehicle management system may notify the individual that maintenance isrequired and/or that one or more operating parameters of the lightelectric vehicle may be changed. In some examples, the notification maybe provided to the individual during the ride or may be provided to theindividual once the individual has reached her destination. Thenotification may inform the individual of the maintenance event,indicate the type of maintenance that is required and provide one ormore instructions on how to properly perform the maintenance.

Although the light electric vehicle management system may provideinstructions to the individual on how to perform the maintenance, theindividual may not feel comfortable performing the maintenance, bequalified to perform the maintenance, have the time to perform themaintenance, and/or have the necessary tools to perform the maintenance.As such, the light electric vehicle management system may store profileinformation of various individuals and only provide the maintenancenotification and/or instructions to those individuals that are qualifiedto perform the determined maintenance.

In yet another implementation, when the light electric vehiclemanagement system determines or otherwise detects a maintenance event,the current location and/or destination of the light electric vehicle isdetermined and/or anticipated. When this information is determined, thelight electric vehicle management system may identify, using securelystored profile information of various individuals, one or moreindividuals that are within a threshold distance (e.g., one mile orless, two miles or less, three miles or less, etc.) from the location(or anticipated destination) of the light electric vehicle. The lightelectric vehicle management system may generate a notification of themaintenance event and provide the notification to a computing deviceassociated with the one or more individuals. In some examples, thenotification may include the detected issue, a determined action to beperformed and the current location (or anticipated destination) of thelight electric vehicle.

In either scenario explained above, when the individual has performedthe requested action or maintenance, the sensors of the light electricvehicle may gather additional light electric vehicle informationcorresponding to the component or part of the light electric vehicle onwhich maintenance was performed. This information may be provided to thelight electric vehicle management system. The light electric vehiclemanagement system may use the additional information to determinewhether the maintenance was performed properly. The light electricvehicle management system may then generate an additional notificationthat indicates whether the maintenance was performed properly andprovide the additional notification to the computing device of theindividual.

As discussed above, the sensor information may be used in combinationwith the rider profile information, and/or requested additional sensorinformation to diagnose or otherwise determine a maintenance eventand/or determine why the light electric vehicle is operating below theoperation threshold.

For example, When the light electric vehicle management system detects amaintenance event or otherwise identifies an issue that is causing thelight electric vehicle to operate below an operation threshold, thelight electric vehicle management system may determine whether the issuecan be addressed and/or resolved by sending one or more instructions toa control system of the light electric vehicle or whether the issueshould be addressed and/or resolved by having the light electric vehicleserviced by a technician. If the issue can be addressed or resolved bysending one or more instructions to the control system of the lightelectric vehicle, the light electric vehicle management system sends theone or more instructions to the control system of the light electricvehicle.

For example, a riding parameter associated with a current rider may bereceived by the light electric vehicle management system. The lightelectric vehicle management system may compare the current ridingparameter to riding parameters associated with stored and/or receivedrider profile information associated with the current rider. Thecomparison may indicate that the current rider is riding the lightelectric vehicle along a particular route at a lower rate of speed thanthe current rider normally rides the light electric vehicle along thatparticular route. In such examples, the light electric vehiclemanagement system may request sensor information from one or moresensors associated with the light electric vehicle in order to determinethe cause for the lower rate of speed.

When the sensor information is received, the light electric vehiclemanagement system may determine that an electric assist motor of thelight electric vehicle is not providing sufficient power to the lightelectric vehicle to enable the current rider to maintain theirdetermined normal rate of speed along the particular route or part ofthe route. In such examples, the light electric vehicle managementsystem can send one or more instructions to the control system of thelight electric vehicle. The control system can use the instructions tocause the electric assist motor to provide additional power to help thecurrent rider reach and/or maintain her determined normal rate of speedalong the route.

In another example, the light electric vehicle management system mayreceive sensor information from a light electric vehicle and use thesensor information to build a rider profile of a particular individual.The rider profile may include information about whether the individualis an aggressive rider or a passive rider (e.g., referred to herein as a“rider type” or a “type of rider”), known riding routes of theindividual (e.g., a route between work and home), frequency of ride/userequests, and so on. The light electric vehicle management system canuse the rider profile to match the particular rider with a particularlight electric vehicle that matches the rider type and provide thelocation of that light electric vehicle to a computing device of theparticular rider.

The light electric vehicle management system may create a set ofpredefined rider profiles based, at least in part, on one or more ridertypes. For example, the set of predefined rider profiles may include anexperienced rider profile, a new rider profile, a power rider profile, acommuter profile, an aggressive rider profile, etc. Based on profileinformation associated with an individual and/or past riding informationassociated with the individual, the individual may be placed in,associated with and/or moved between these various predefined groups.The light electric vehicle management system may then match a particularindividual to a particular light electric vehicle that is more suited tothe individual based, at least in part, on the assigned predefinedgroup.

For example, when the particular rider sends a use request to the lightelectric vehicle management system, the light electric vehiclemanagement system may determine which light electric vehicles in alocation associated with the particular rider are more suited to theriding style of the particular rider. The location of the identifiedlight electric vehicles may then be provided to a computing device ofthe particular rider.

Accordingly, the present disclosure provides a plurality of technicalbenefits including but not limited to improving maintenance downtime forlight electric vehicles by detecting or predicting maintenance events asthe maintenance events occur or prior to one occurring, improving a userexperience of light electric vehicles by ensuring the light electricvehicle is operating as expected and by matching individuals to lightelectric vehicles that have features or performance characteristics thatmatch the riding style of the individual, improving the safety of theriders of light electric vehicles among other examples.

These and other features will be described in more detail below withrespect to FIG. 1-FIG. 10.

FIG. 1 illustrates an example environment 100 in which aspects of thepresent disclosure may be practiced. As illustrated, environment 100includes an electric scooter(s) 110, an electric bicycle(s) 130, and arechargeable battery kiosk(s) 150. It will be appreciated that theelectric scooter 110 and the electric bicycle 130 are provided asexample light electric vehicles and that, in other examples, aspectsdescribed herein apply to other types of light electric vehicles.

As described herein, the environment 100 includes a network service thatreceives information from the electric scooter 110 and/or the electricbicycle 130 (also referred to herein as light electric vehicles) over anetwork communication channel (e.g., one or more networks, the Internet,etc.). The information enables a user, using a client applicationexecuting on a computing device, to locate, request, and/or reserve(e.g., rent or borrow for a duration of time) one or more light electricvehicles.

In some examples, the network service includes one or more computingsystems or servers that are remote from the computing device of the userand the light electric vehicles. The one or more computing systemsincludes an application programming interface (API) that enables the oneor more computing systems to receive information from, send informationto, and otherwise interact with the computing device, the light electricvehicles 110, 130 and/or the rechargeable battery kiosk(s) 150.

For example, the client application executing on the computing device ofthe user receives, from the network service over the networkcommunication channel, information about a location of one or more ofthe light electric vehicles. The location of each of the light electricvehicles can then be provided on a user interface of the clientapplication.

In one example, the user interface of the client application includes amap that displays a determined location of the user and/or a determinedlocation of the light electric vehicles. In some examples, thedetermined location of the user and/or the determined location of thelight electric vehicles is based, at least in part, on GlobalPositioning System (GPS) data (or other location information) receivedby the network service over the network communication channel.

The user interface of the client application displays the locationinformation of the user and the light electric vehicles as differenticons (or other such representations). Once the location information isdisplayed, the user may select an icon representing a type of lightelectric vehicle (e.g., an icon for an electric scooter 110 or an iconfor an electric bicycle 130). The user interface of the clientapplication then generates or determines a route (e.g., providesdirections) from the user's current location to the selected lightelectric vehicle. Selection of one of the icons may also enable the userto reserve (e.g., place a hold on) the light electric vehicle (to ensurethat the light electric vehicle will be at the determined location whenthe user arrives), rent the light electric vehicle and/or borrow thelight electric vehicle for a period of time.

Each light electric vehicle and/or the network service also includes alocation tracking system that tracks, receives and/or determines alocation of each light electric vehicle as they are used. In someexamples, the location tracking system tracks the location informationof the light electric vehicle in real-time or substantially real-time.In other examples, the location tracking system determines the locationinformation of the light electric vehicle at periodic intervals (e.g.,every minute, every five minutes, every ten minutes, etc.). In yet otherexamples, the location tracking system may track the location of thelight electric vehicle in real-time or substantially real-time when thelight electric vehicle is reserved, rented or otherwise used by a userand may track location information at periodic intervals when the lightelectric vehicle has been reserved or is otherwise not in use.

The one or more computing systems of the network service also includeone or more databases that store information about each of the lightelectric vehicles and/or the rechargeable battery kiosk(s) 150. Forexample, the one or more databases may store location information foreach light electric vehicle and/or the rechargeable battery kiosk(s)150, rechargeable battery status information for rechargeable batteriesused by each light electric vehicle and/or in the rechargeable batterykiosk(s) 150, rechargeable battery kiosk information (e.g., the numberof rechargeable batteries housed by the rechargeable battery kiosk 150),and/or light electric vehicle status information (e.g., how many timesthe light electric vehicle has been used, whether the light electricvehicle is damaged, whether the light electric vehicle should beserviced etc.).

The one or more databases may also store information about the user.This information may include a profile of the user (e.g., username,contact information, etc.) security credentials of the user (e.g., apassword), historical usage data, payment information and the like.

The one or more computing systems of the network service may alsoinclude a matching system. The matching system receives, manages orotherwise handles various requests from the user. The requests mayinclude light electric vehicle rental requests and light electricvehicle reservation requests. For example, when a vehicle rental requestis received from the client application executing on the user'scomputing device, the matching system may communicate with the locationtracking system and determine which light electric vehicle should bematched with or otherwise assigned to the requesting user.

The one or more computing systems of the network service may alsoinclude a payment system that processes payment information of the user.For example, when a user rents and uses a light electric vehicle, theuser may be charged for the usage based on a duration of use and/or atravel distance. Once the user has finished using the light electricvehicle (e.g., by arriving at their intended destination, a check-inpoint, a rechargeable battery kiosk 150, etc.), the payment system mayautomatically process the payment information of the user.

As discussed above, the environment 100 includes one or more lightelectric vehicles including, but not limited to, an electric scooter 110and an electric bicycle 130. In examples, the electric scooter 110includes vehicle components (e.g., wheels, axles, baseboard, handlebar,braking mechanisms, etc.), one or more electric motors, control systems,sensors, speakers, and/or lights, which may be powered by a rechargeablebattery. The rechargeable battery may be secured to the electric scooter110 by a battery holster 120.

Likewise, and in some examples, the electric bicycle 130 includesvehicle components (e.g., wheels, axles, chains, gear ratios, bicycleseat, handlebar, bicycle frame, braking mechanisms, etc.), one or moreelectric motors, control systems, sensors, speakers, and/or lights,which may also be powered by a rechargeable battery. The rechargeablebattery may be secured to the electric bicycle 130 by a battery holster140.

The control system of the electric scooter 110 and/or the electricbicycle 130 manages the power output to the one or motors, provides avisual indication as to a charge level of the rechargeable battery inthe battery holster 120, and/or communicates directly (e.g., via Wi-Fi,Bluetooth, etc.) or indirectly (e.g., via one or more remote computingdevices, one or more networks, the Internet, etc.) with the computingdevice of the user and/or with the network service.

Example communications include, but are not limited to, initiatinglocking or unlocking of the electric scooter 110 or the electric bicycle130 (e.g., initiating or ending a travel session), initiating a batteryswap to exchange a rechargeable battery in the battery holster 120 orthe battery holster 140 with one in a rechargeable battery kiosk 150,determining a location and/or status information of the electric scooter110 or the electric bicycle 130, and determining a location of arechargeable battery and/or a rechargeable battery kiosk 150. Lights,speakers, and/or other output devices of the electric scooter 110 or theelectric bicycle 130 may be used to provide an indication as to thelocation of the electric scooter 110 or the electric bicycle 130 or asan anti-theft mechanism, among other examples.

As shown in FIG. 1, each light electric vehicle includes a batteryholster. For example, the battery holster 140 is affixed to the seattube of the electric bicycle 130, while the battery holster 120 isillustrated as being affixed to the handlebar column of the electricscooter 110. It will be appreciated that the locations of the batteryholsters 120 and 140 are provided as examples, and that a batteryholster may be positioned in a variety of alternate locations in otherexamples. For example, the battery holster 140 may be affixed to thehandlebar column or the cross bar of the electric bicycle 130. Asanother example, the battery holster 120 may be affixed to the deck orlocated near the rear of the electric scooter 110.

The battery holsters 120 and 140 are each operable to receive arechargeable battery. For example, an individual user may operate alight electric vehicle for a period of time and then determine that therechargeable battery in use by the light electric vehicle needs to berecharged. In some instances, the light electric vehicle, or therechargeable battery itself, may communicate current battery chargeinformation for the rechargeable battery to the computing device of theuser. In another example, the rechargeable battery and/or batteryholster 120 and 140 may include a visual indicator to display the chargelevel of the rechargeable battery. As an addition or an alternative, theelectrical vehicle, or the rechargeable battery itself, may communicatecurrent battery charge information for the rechargeable battery to thenetwork service, which can provide battery information to the computingdevice of the user. When this occurs, the user may be directed to arechargeable battery kiosk 150. For example, the network service cantransmit data, over one or more networks, to the computing device tocause the computing device to display information about a particularrechargeable battery kiosk 150 to travel to.

When the user arrives at the rechargeable battery kiosk 150, the usermay exchange the light electric vehicle's current battery with anotherrechargeable battery housed by the rechargeable battery kiosk 150,thereby enabling the light electric vehicle to continue or resumeoperation. In some instances, the user can use the client applicationexecuting on the computing device of the user to locate and/or select arechargeable battery kiosk 150, receive directions to the rechargeablebattery kiosk 150, and initiate a battery swap with the rechargeablebattery kiosk 150 when the user arrives at its location.

According to examples, when a battery swap is initiated, the controlsystem of the light electric vehicle may enable the rechargeable battery160 to be removed from a battery holster, such as battery holster 120 or140. The rechargeable battery 160 may then be exchanged for a differentrechargeable battery 160 housed by the rechargeable battery kiosk 150.The rechargeable battery 160 may subsequently be inserted into thebattery holster of the light electric vehicle.

The rechargeable battery kiosk 150 stores and charges a set ofrechargeable batteries 160. Each rechargeable battery 160 in the set canbe used by both the electric scooter 110 and the electric bicycle 130.In some examples, multiple rechargeable battery kiosks 150 are locatedwithin a city, county, or other geographic region. For example, onerechargeable battery kiosk may be located in or otherwise associatedwith a first geographic area within a geographic region and anotherrechargeable battery kiosk may be located in or otherwise associatedwith a second geographic area within the geographic region.

Thus, when a user is traveling through the geographic region on an lightelectric vehicle and wants or needs to exchange the light electricvehicle's current rechargeable battery for one that has more charge, theuser may be directed (e.g., via the client application executing on theuser's computing device) to the rechargeable battery kiosk 150associated with the geographic region. When the user arrives at therechargeable battery kiosk 150, the user can exchange their currentrechargeable battery for one that is fully charged or substantiallyfully charged. This enables the user to travel using a light electricvehicle across distances that may otherwise not be possible using thepower provided by one charge of a rechargeable battery.

In some examples, the rechargeable battery kiosk 150 comprises a controlsystem that communicates directly or indirectly with a computing deviceof the user when performing a battery swap such as described above. Inexamples, the control system communicates with a remote computingdevice(s), e.g., that implements the network service, using a connectionto one or more networks, such as a Wi-Fi network and/or a cellularnetwork. The rechargeable battery kiosk 150 may receive and/or reportrechargeable battery status information to a remote computing device(s).The battery status information can include, but is not limited to,battery charge levels, battery health, an amount of rechargeablebatteries currently available at the rechargeable battery kiosk, and/orusage demand statistics.

FIG. 2A illustrates a system 200 for detecting a maintenance event forlight electric vehicles 235 according to an example. The system 200 maybe used with any number of different light electric vehicles 235including electric bicycles, electric scooters, and so on. Although FIG.2A illustrates a single electric bicycle and a single electric scooter(collectively referred to as light electric vehicle(s) 235), the system200, and more specifically, the light electric vehicle management system205, may detect maintenance events, determine the cause of themaintenance events and determine how to address the maintenance eventsfor a number of different light electric vehicles individually or at thesame time or substantially the same time.

The system 200 includes a light electric vehicle management system 205.The light electric vehicle management system 205 may include a riderprofile system 210, a maintenance system 215, a route/locationinformation system 220 and an instruction management system 225. Inorder to detect a maintenance event, the light electric vehiclemanagement system 205 may receive different types of information from avariety of different sources.

For example, and as shown in FIG. 2A, the light electric vehiclemanagement system 205 may receive light electric vehicle information 245and/or riding parameter information 240 from a light electric vehicle235 over a network 230. Additionally, the light electric vehiclemanagement system 205 may receive rider profile information 250 from acomputing device 255 associated with an individual over the network 230.As will be explained in more detail below, the light electric vehiclemanagement system 205 may use the received information to detect amaintenance event, determine the cause of the maintenance event anddetermine how to address the maintenance event.

For example, when an individual wants to reserve and use a lightelectric vehicle 235, the individual may access an application executingon the computing device 255 and submit a reservation request (alsoreferred to as use request), over the network 230, to the light electricvehicle management system 205. In some examples, the applicationexecuting on the computing device 255 may provide rider profileinformation 250 to the rider profile system 210 of the light electricvehicle management system 205.

Although the light electric vehicle management system 205 collectsvarious types of data related to the individual, in some examples, theindividual may control or otherwise indicate what information and/orwhat types of information the light electric vehicle management system205 can request, receive and/or store. For example, an individual mayeither opt in or opt out of any data collection process describedherein. This may include indicating data that can be collected and/orstored by the systems described herein and which data cannot becollected and/or stored by the systems described herein.

The rider profile information 250 may contain profile information aboutthe individual that submitted the reservation request. For example, therider profile information 250 may contain information about the numberof times the individual has reserved and/or used light electric vehicles235, one or more routes taken by the individual while using lightelectric vehicles 235, the times of day and/or days of the week theindividual reserved and/or used light electric vehicles 235, lightelectric vehicle riding habits of the individual (e.g., how fast theindividual typically rides light electric vehicles 235, a pedalingcadence of the individual, amount of power of a rechargeable batterythat is typically consumed by the light electric vehicle 235), whetherthe individual has been trained or is otherwise certified to performmaintenance, service and/or repairs of light electric vehicles 235, andso on.

For example, the rider profile information 250 may include informationthat the individual typically reserves a light electric vehicle 235 onMonday, Wednesday and Friday mornings at 7:00 AM. The rider profileinformation 250 may also indicate that the individual typically reservesthe light electric vehicle 235 at or near a particular origin (e.g.,near the individual's home) and travels a particular route to aparticular destination (e.g., to the individual's work). Likewise, therider profile information 250 may indicate that the individual typicallyreserves a light electric vehicle on Monday, Wednesday and Fridayevenings at 6:00 PM and takes a particular route from an origin (e.g.,the individual's work) to a destination (e.g., the individual's home).

The rider profile information 250 may also include information aboutlight electric vehicle riding habits of the individual along theparticular route, on those particular days and/or those particular timesof the day. For example, the rider profile information 250 may indicatethat the individual typically rides ten miles-per-hour during theindividual's morning commute from the particular origin to theparticular destination. The rider profile information 250 may alsoindicate that the individual pedals at a particular cadence and causesthe light electric vehicle 235 to consume five percent of the power in arechargeable battery of the light electric vehicle 235. Likewise, therider profile information 250 may indicate that the individual's eveningcommute from the particular origin to the particular destination hassimilar or different riding parameters. Although specific riding habitsand values are mentioned, these are for example purposes only.

The rider profile information 250 may also include information as towhether the individual has been trained or is otherwise certified (e.g.,has a particular certification level) to perform maintenance on thelight electric vehicle 235. The certification level may includeinformation regarding one or more actions the individual is authorizedto perform on the light electric vehicles 235. In some examples, theactions may be related to or otherwise address a particular maintenanceevent.

As used herein, the term “maintenance” means to perform one or morerepairs to the light electric vehicle 235 and/or perform one or moreservices. These repairs and/or services may include repairing and/orreplacing one or more tires on the light electric vehicle 235, repairingand/or replacing one or more wheels on the light electric vehicle 235,repairing and/or replacing one or more spokes of the wheels of the lightelectric vehicle 235, repairing detected electrical faults of the lightelectric vehicle 235, repairing detected alignment issues, repairing orreplacing a drivetrain of the light electric vehicle 235, repairingand/or replacing one or more brakes and/or a braking system of the lightelectric vehicle 235, and so on. Although specific repairs arementioned, the rider profile information 250 may indicate thecertification level of the individual and whether the individual canperform various other types of repairs and services. Additionally, thecertification level of some individuals may indicate that they aretrained or are otherwise authorized to perform a first set or type ofmaintenance and/or repairs but not a second type of maintenance and/orrepairs while the certification level of other individuals may indicatethat they are trained to perform any type of requested maintenanceand/or repairs.

The rider profile information 250 may be provided to the rider profilesystem 210 each time a light electric vehicle 235 is reserved and/orused by the individual. In other examples, the rider profile system 210may receive and use sign-in credentials from the computing device 255associated with the individual to access rider profile information 250that has been securely stored in the rider profile system 210. Thestored rider profile information 250 may be updated as new or additionalinformation (e.g., additional routes taken by the individual, changes inriding habits, updates to maintenance authorization status, etc.) isreceived from the computing device 255.

For example, the rider profile information 250 may include rider habitinformation. The rider habit information may be provided to the riderprofile system 210 in real-time or substantially real-time as theindividual is riding a light electric vehicle 235. Thus, the lightelectric vehicle management system 205 may be able to detect changes tothe individual's riding habits and determine, in real-time orsubstantially real-time, if those changes are due to a maintenance eventor if the changes are potentially due to a condition of the rider (e.g.,the rider is simply riding slower, potentially not feeling well, etc.).

As briefly discussed above, rider habit information may includeinformation about a pedaling cadence of the individual as the individualrides the light electric vehicle 235, an average or typical speed atwhich the individual rides the light electric vehicle 235, an averageamount of power of a rechargeable battery used by the light electricvehicle 235 when the individual is riding the light electric vehicle 235(e.g., how much the individual pedals the light electric vehicle 235versus relying on the electric assist motor of the light electricvehicle 235), gear ratio shifting habits (e.g., how often, when andwhere along a route the individual shifts gear ratios) of theindividual, and so on.

The rider habit information may also be used to determine whether theindividual has different riding habits based on, for example, time ofthe day, day of the week, location, anticipated route, and so on. Forexample, an individual may have a first set of riding habits during theweek as the individual commutes from home to work. However, theindividual may have a second set of riding habits on the weekend. Eachof these different riding habits, and detected changes to the differentriding habits, may be used to detect a maintenance event.

Although the above examples indicate that route information and/or riderhabit information is received from a computing device 255, in someinstances, the rider profile system 210 may receive route information,rider habit information, reservation information and/ororigin/destination information of the individual from the light electricvehicle 235. For example, the light electric vehicle 235 may provide GPSdata or other location information to the light electric vehiclemanagement system 205. Likewise, the light electric vehicle managementsystem 205 may receive rider habit information (e.g., gear ratioshifting habits, average speed, pedaling cadence, etc.), represented asriding parameter 240 information, from the light electric vehicle 235.The light electric vehicle management system 205 may store the receivedinformation in the rider profile system 210 associated with theindividual that reserved and is riding the light electric vehicle 235.In some examples, the route information and/or location information ofthe light electric vehicle 235 may be received and/or stored by theroute/location information system 220.

The route/location information system 220 may also receive and/or storetopology information about a particular route. The topology informationmay be used to help determine whether a detected decrease in performancemetrics, either by the individual riding the light electric vehicle 235and/or by the light electric vehicle 235, is a potential maintenanceevent or is based, at least in part, on a current location of the lightelectric vehicle 235.

For example, if the light electric vehicle management system 205receives riding parameter information 240 indicating that the individualis riding the light electric vehicle 235 more slowly than usual, theroute/location information system 220 may be able to determine, based onreceived current location information of the light electric vehicle 235,that the individual is riding the light electric vehicle 235 up a hill.As such, the decrease in speed of the light electric vehicle 235 may bebased on the location of the light electric vehicle 235 and not theresult of a maintenance event.

The light electric vehicle management system 205 may also be able toaccurately predict, determine and/or anticipate a route of travel of theindividual using the rider profile information 250. In some examples,this includes determining or anticipating different topographies along aroute or an anticipated route. For example, if the individual reservesthe light electric vehicle 235 at 7:00 AM on Monday morning, the lightelectric vehicle management system 205 may determine, based on riderprofile information 250, that the individual is going to work. The lightelectric vehicle management system 205 may also determine, using riderprofile information 250, that the individual will most likely take aparticular route on the way to work.

Using this information, the light electric vehicle management system 205may determine or otherwise anticipate riding parameters of theindividual along the route. The anticipated riding parameters (or storedriding parameters of the individual on past routes) may be compared withactual riding parameters 240 of the individual (e.g., riding parameter240 information received in real-time or substantially real time as theindividual is riding the light electric vehicle 235 along the route) todetermine whether the light electric vehicle 235 may be experiencing amaintenance event.

For example, if the anticipated riding parameters are within asimilarity threshold of the actual riding parameters 240, the lightelectric vehicle management system 205 may determine the light electricvehicle 235 is operating as expected. As such, no maintenance event isoccurring. However, if the anticipated riding parameters are not withina similarity threshold of the actual riding parameters 240, the lightelectric vehicle management system 205 may determine that the lightelectric vehicle 235 is not operating as expected. As such, amaintenance event may be occurring and the light electric vehiclemanagement system 205 may request light electric vehicle information 245from the light electric vehicle 235.

As briefly discussed above, the light electric vehicle management system205 may also receive light electric vehicle information 245 from thelight electric vehicle 235 over the network 230. The light electricvehicle information 245 may include information about one or moreoperating parameters of the light electric vehicle 235. In someexamples, the light electric vehicle information 245 may be collected byone or more sensors associated with the light electric vehicle 235. Theinformation collected by the sensors may be used to determine whetherthe light electric vehicle 235 is operating below an operation thresholdand/or whether various components of the light electric vehicle 235 areoperating as expected.

For example, the light electric vehicle 235 may have a sensor that readsthe tire pressure of the light electric vehicle 235, a sensor thatdetects an amount of torque that is being applied to one or more pedalsof the light electric vehicle 235, a sensor that detect an amount oftraction provided by the tires of the light electric vehicle 235, and soon. In other examples, the information from the one or more sensors maybe used to determine performance metrics of the light electric vehicle235. The performance metrics of the light electric vehicle 235 mayinclude a rechargeable battery usage rate of the light electric vehicle235, an average or top speed of the light electric vehicle 235, howquickly the light electric vehicle 235 can accelerate, how long it takesthe light electric vehicle 235 to stop when one or more brakes areapplied in relation to, for example, how hard the individual riding thelight electric vehicle 235 is applying the brakes, balancecharacteristics (e.g., whether the alignment of the tires and/or spokesof the wheel(s) of the light electric vehicle 235 cause the lightelectric vehicle 235 to be wobbly) of the light electric vehicle 235, anamount of power provided by an electric assist motor of the lightelectric vehicle 235, and so on. Although specific sensors arementioned, the light electric vehicle 235 may have any number of sensorsthat detect and/or determine a status of various components or parts ofthe light electric vehicle 235.

When this information is received by the light electric vehiclemanagement system 205 (e.g., via an API and/or over the network 230),the light electric vehicle management system 205 may determine, usingthe received information, whether the light electric vehicle 235 isexperiencing a maintenance event. In other examples, while a maintenanceevent may not be currently occurring, the light electric vehiclemanagement system 205 can use the received information to anticipate amaintenance event. For example, if the received information is trendingin such a way as to indicate a maintenance event will occur, the lightelectric vehicle management system 205 may take preemptive actions toremedy the anticipated maintenance event.

The information may also be used to determine whether the change ordecrease in performance of the light electric vehicle 235 is due, atleast in part, to the individual that is riding the light electricvehicle 235. For example, if the operating parameters of the lightelectric vehicle 235 indicate that the various components or systems ofthe light electric vehicle are operating as expected, the light electricvehicle management system 205 may determine that the individual is thecause for the decrease in performance.

For example, one or more torque and/or cadence sensors associated withthe light electric vehicle 235 may provide information about the amountof force the individual is applying to one or more pedals of the lightelectric vehicle 235 and/or how fast the individual is pedaling thelight electric vehicle 235. The light electric vehicle management system205 may compare the received information with previously received torqueand/or cadence sensor information associated with the individual anddetermine that the individual is fatigued. As such, the light electricvehicle management system 205 may adjust an operating parameter of thelight electric vehicle 235 such that an electric assist motor of thelight electric vehicle 235 provides additional power to help theindividual maintain their desired or typical speed.

In another example, one or more sensors (e.g., a steering sensor)associated with the light electric vehicle 235 may detect that the lightelectric vehicle 235 is swerving, the position of the handlebar isaskew, and/or the light electric vehicle 235 is generally unstable.Using this information, the light electric vehicle management system 205may determine that the individual is intoxicated. As such, the lightelectric vehicle management system 205 may change one or more operatingparameters of the light electric vehicle 235 (e.g., by ending a useperiod of the light electric vehicle 235 or causing the electric assistmotor of the light electric vehicle 235 to stop providing power to thelight electric vehicle). Although specific examples have been given, thelight electric vehicle management system 205 may use sensor informationto determine or detect any number of rider conditions.

In yet another example, received sensor information may indicate one ormore issues in an environment in which the light electric vehicle isoperating. For example, if a steering position sensor on multipledifferent light electric vehicles 235 provides information to the lightelectric vehicle management system 205 that multiple different ridersalong a particular route swerve at or near the same location, the lightelectric vehicle management system 205 may determine that there is anissue (e.g., a pothole or other roadway hazard) with the environment inwhich the light electric vehicle 235 is operating.

Similarly, sensors of one or more light electric vehicles 235 may detectthat one or more tires of the light electric vehicle 235 slip at aparticular location along a route. As such, the light electric vehiclemanagement system 205 may determine that there is gravel, mud, loosedirt etc. on a road or path.

In such examples, the light electric vehicle management system mayprovide a notification 285 to the computing device 255 associated withthe individual that the individual is approaching a hazard, that one ormore operating parameters of the light electric vehicle 235 may or willbe changed (at least temporarily) and/or send instructions to the lightelectric vehicle 235 that change one or more operating parameters of thelight electric vehicle 235. For example, the light electric vehiclemanagement system 205 may cause a top speed (or current speed) of thelight electric vehicle 235 to be reduced until the individual has passedthe detected hazard. The notification 285 may be a visual notification,an audible notification and/or a haptic/tactile notification.

Referring back to the previous example in which the maintenance event iscaused by one or more components or systems of the light electricvehicle 235, the light electric vehicle management system 205 maydetermine whether the maintenance event can be addressed remotely orwhether the maintenance event is only addressable by a technician. Forexample, the light electric vehicle management system may determinewhether the maintenance event can be addressed by sending one or moreinstructions to the light electric vehicle 235 or whether themaintenance event should be addressed by a technician or otherindividual that has the training, certification level and/or experienceto address the maintenance event.

For example, when the light electric vehicle management system 205receives the light electric vehicle information 245 and/or the ridingparameter information 240, the received information may be provided tothe maintenance system 215. The maintenance system 215 may use thisinformation to detect whether a maintenance event is occurring, whethera maintenance event is likely to occur, determine what is causing themaintenance event and determine how the maintenance event should beaddressed. Once the maintenance system 215 determines the cause of themaintenance event and how to address the maintenance event, theinstruction management system 225 may provide instructions on how toaddress the maintenance event to one or more of the light electricvehicle 235, the computing device 255 associated with the individualriding the light electric vehicle 235 or another individual that iscertified or otherwise trained to perform one or more maintenanceactions on the light electric vehicle 235.

For example and referring to FIG. 2B, when the maintenance system 215determines that a maintenance event is occurring, will occur, or hasoccurred, the maintenance system 215 may determine the cause of themaintenance event and one or more possible solutions that address(either temporarily or permanently) the maintenance event. As part ofthis process, the maintenance system 215 may determine whether themaintenance event can be addressed remotely (e.g., by sending one ormore instructions 270 to the light electric vehicle 235) or whether atechnician or other individual should provide maintenance to orotherwise service the light electric vehicle 235.

For example, if the maintenance system 215 determines, based on receivedriding parameter 240 information and/or light electric vehicleinformation 245, that the electric assist motor of the light electricvehicle 235 is not providing a sufficient amount of power to the lightelectric vehicle 235, the maintenance system 215 may determine that thisparticular maintenance event can be addressed, at least temporarily, byenabling the electric assist motor to output more power. As such, theinstruction management system 225 may provide these instructions 270 toa computing device or control system associated with the light electricvehicle 235. In some examples, the light electric vehicle managementsystem 205 may also send a notification 285 to the computing device 255associated with the individual that the light electric vehicle 235 isexperiencing (or has experienced) a maintenance event and how themaintenance event is (or was) addressed.

In another example, the maintenance system 215 may detect, based onreceived sensor information, a high resistance or an increase in currentbetween the rechargeable battery of the light electric vehicle 235 andan electric assist motor of the light electric vehicle 235. In thisexample, the maintenance system 215 may determine that the lightelectric vehicle has faulty wiring. As such, the maintenance system 215may determine that this particular maintenance event can only beaddressed by an individual with the certification level or other suchqualifications or experience to fix or repair the faulty wiring.

The maintenance system 215 may interact with the rider profile system210 to determine whether the individual that is currently riding thelight electric vehicle 235 has been trained or is otherwise qualified toaddress this particular maintenance event (e.g., the faulty wiring). Ifthe rider profile information 250 of the individual indicates that sheis trained or is otherwise qualified to perform an action that addressesthe maintenance event, the instruction management system 225 maytransmit the requested action 265, along with one or more instructionson how to perform the requested action 265, to the computing device 255associated with the individual.

In other examples, the maintenance system 215 may determine, based onrider profile information 250, that the individual that is currentlyriding the light electric vehicle 235 has not been trained to fix orotherwise address the detected maintenance event. In such examples, thelight electric vehicle management system 205 may send a notification 285to the computing device 255 associated with the individual to notify theindividual that the light electric vehicle 235 is experiencing (or hasexperienced) a maintenance event.

In some examples, the notification 285 may also include instructionsabout how the individual should proceed. For example, the notificationmay indicate that the individual should proceed to their intendeddestination, that the individual should end their use as soon aspossible, or that the individual should take the light electric vehicle235 to a particular destination so the light electric vehicle 235 can beserviced. In some examples, the individual may be provided with anincentive for following the instructions in the notification 285.

When the maintenance system 215 determines the individual does not havean appropriate certification level or has not been trained to addressthe maintenance event, the maintenance system 215 may interact with therider profile system 210 and/or the route/location information system220 to determine a current location of the light electric vehicle 235and/or an anticipated destination of the light electric vehicle 235(e.g., based, at least in part, on rider profile information 250 of theindividual that is currently riding the light electric vehicle 235). Thelight electric vehicle management system 205 may also determine whetherthere are any individuals at or near the current location and/oranticipated destination that have the training or experience to addressthe maintenance event.

For example, when the maintenance event is detected, the maintenancesystem 215 may interact with the rider profile system 210 to determinethe location of one or more individuals that have the training orcertification level to address the detected maintenance event. Oncethose individuals have been identified, the maintenance system 215and/or rider profile system 210 may determine which of those individualsare at or near to the current location of the light electric vehicle 235or the anticipated destination of the light electric vehicle 235. Theinstruction management system 225 may then provide a requestedaction/location 280 of the light electric vehicle 235 to a computingdevice 275 associated with the identified individual.

When the requested action/location 280 is received by the identifiedindividual, the identified individual may have the opportunity to acceptperformance of the requested action or deny the request. In someexamples, if the identified individual accepts the request, theidentified individual may be provided an incentive (e.g., payment,discounts on future rides, etc.) for performing the requested action. Insome examples, the location of the light electric vehicle 235 is notprovided to the identified individual until the currentreservation/riding period of the light electric vehicle 235 is complete.In other examples, the individual that is riding the light electricvehicle may be provided a notification (e.g., on her computing device255 and/or on a display of the light electric vehicle 235) and/or anincentive to take the light electric vehicle 235 to a location at ornear the location of the identified individual so the identifiedindividual can perform the requested action 280. At that point, theindividual may end their reservation of the light electric vehicle 235and/or start another reservation period with a different light electricvehicle 235.

When the requested action is performed (e.g., either by the individualthat is currently riding the light electric vehicle or by the identifiedindividual), the light electric vehicle 235 may send additional lightelectric vehicle information 260 to the light electric vehiclemanagement system 205. The additional light electric vehicle information260 may be used by the maintenance system 215 to determine whether themaintenance event was addressed correctly and/or completely. Forexample, if the requested action 260/280 relates to addressing a tirepressure issue for the light electric vehicle 235, the additional lightelectric vehicle information 260 may contain tire pressure sensorinformation in order to determine whether the requested action 260/280was taken and/or whether it was performed correctly.

As discussed above, a maintenance event may be detected by themaintenance system 215 based on riding parameter 240 information and/orlight electric vehicle information 245. However, in some examples, themaintenance system 215 may require additional information to help ensurethe diagnosis of the maintenance event is correct. For example, if theriding parameter 240 information indicates the individual riding thelight electric vehicle 235 is traveling at a lower rate of speed along aparticular route than the individual has previously traveled, but themaintenance system 215 cannot, with the current information diagnose amaintenance event, the maintenance system 215 may request additionallight electric vehicle information 260 to help determine whether amaintenance event is occurring. If the light electric vehicle 235 isexperiencing a maintenance event, the maintenance event may be addressedsuch as previously described.

Although the examples provided above disclose how maintenance events canbe detected in real-time or substantially real-time, and how thosemaintenance events can be addressed, the system 200 may also predictwhether a maintenance event is likely to occur in the future. Forexample and as described above, the light electric vehicle managementsystem 205 may receive riding parameter 240 information and/or lightelectric vehicle information 245. Using this information, the lightelectric vehicle management system 205 may be able to anticipate whethera particular type of maintenance event will occur and preemptivelyaddress the maintenance event.

For example, if the riding parameter 240 information indicates that anindividual is pedaling more often along a particular route or part of aroute than the individual has typically done in the past, or theindividual is shifting gears more often along a particular route or partof the route, the light electric vehicle management system 205 mayrequest additional light electric vehicle information 260 from the lightelectric vehicle 235 and/or provide instructions 270 to the lightelectric vehicle 235 such as previously described. The instructions 270may be used to increase the amount of power provided by the electricassist motor to help the individual maintain their average speed alongthe route. Thus, the instructions may preemptively address theanticipated maintenance event before it impacts the individual ridingthe light electric vehicle 235.

FIG. 3A illustrates an example system 300 for matching an individualwith a light electric vehicle 335 based, at least in part, on adetermined rider type of the individual. The rider type may be based, atleast in part, on rider profile information 345 associated with theindividual. In some examples, the system 300 may be used to match anindividual with a particular riding type and/or a riding preference(e.g., aggressive riders) with a particular light electric vehicle 335.Additionally, the system 300 may be used to identify individuals thathave been trained or are otherwise certified to address maintenanceevents and direct those individuals to light electric vehicles 335 thatneed maintenance.

In some examples, the system 300 may have a set of predefined riderprofiles each of which are associated with a particular rider type. Forexample, the system 300 may include an experienced rider profile, a newrider profile, a power rider profile, an aggressive rider profile and acommuter profile. Although specific rider profiles are mentioned, theseare for example purposes only and the system 300 may have any number ofdifferent predefined rider profiles. Additionally, new rider profilesmay be added and existing rider profiles may be removed and/or edited.

The system 300 may also automatically associate a particular individualwith one or more of the predefined rider profiles based, at least inpart, on profile information associated with the individual and/or past(or current) riding information associated with the individual. When anindividual has been matched or is otherwise associated with a particularpredefined rider profile, the system 300 may match a particularindividual with a particular light electric vehicle having features,functionalities and/or operating parameters that are suited to theriding style/preferences of the individual.

As shown in FIG. 3A, the system 300 includes similar systems to thesystem 200 shown and described with respect to FIG. 2A. It should beunderstood that the systems shown and described with respect to FIG. 3Afunction in a similar manner as the systems shown and described withrespect to FIG. 2A.

For example, the system 300 includes a light electric vehicle managementsystem 305. The light electric vehicle management system 305 includes arider profile system 310, a maintenance system 315, a route/locationinformation system 320 and an instruction management system 325. Thelight electric vehicle management system 305 may receive light electricvehicle information 340 from one or more light electric vehicles 335over a network 330 such as previously described.

The light electric vehicle management system 305 may also receive riderprofile information 345 from a computing device 355 associated with anindividual. The rider profile information 345 may be included orotherwise associated with a reservation request 350 or use request. Thereservation request 350 may be provided to the light electric vehiclemanagement system 305 when the individual wants to reserve a lightelectric vehicle 335.

For example, when an individual wants to reserve and use a lightelectric vehicle 335, the individual may access an application executingon the computing device 355 and submit reservation request 350, over thenetwork 330, to the light electric vehicle management system 305. Insome examples, the application executing on the computing device 355 mayprovide the rider profile information 345 to the rider profile system310 of the light electric vehicle management system 305. In otherexamples, once the individual has been identified by the rider profileinformation 345, the rider profile system 310 may access securely storedprofile information of the individual in order to determine ridinghabits of the individual, a riding profile of the individual a ridertype of the individual, whether the individual is authorized or isotherwise trained to address one or more maintenance events and/orperform one or more services on light electric vehicles 335, a currentlocation of the individual, past routes taken by the individual, and soon.

When the location of the individual is determined, the light electricvehicle management system 305 may determine or identify one or morelight electric vehicles 335 that are in or otherwise associated with thelocation of the individual. Once one or more light electric vehicles 335in or around the location of the individual are identified, themaintenance system 315 may determine whether any of the identified lightelectric vehicles 335 are experiencing, have experienced and/or areanticipated to experience a maintenance event. As previously discussed,the maintenance system 315 may detect a maintenance event based, atleast in part, on light electric vehicle information 340 and/or receivedriding parameter information (e.g., riding parameter 240 information(FIG. 2A)).

Using the rider profile information 345, the light electric vehiclemanagement system 305 may determine whether the requesting individual istrained and/or authorized to address the detected maintenance event. Ifso, the maintenance system 315, the instruction management system 325and/or the route/location information system 320 may provide locationinformation 360 (FIG. 3B) of the light electric vehicle 335 experiencingthe maintenance event and a requested action 365, to the computingdevice 355 associated with the requesting individual.

An example user interface 400 for a computing device showing a requestedaction and an example location of a light electric vehicle is shown inFIG. 4. For example, in response to receiving a reservation request(e.g., reservation request 350 (FIG. 3A)), a light electric vehiclemanagement system may identify that a light electric vehicle,represented by icon 410, near a location of the requesting individual,represented by icon 430, is experiencing a maintenance event. In such anexample, the user interface 400 displays a requested action 420. In thisexample, the requested action 420 is a request for the individual toaddress a tire pressure issue with the light electric vehicle. In someexamples, the user interface 400 may also display or otherwise providean incentive for the individual to perform the requested action 420.

Referring back to FIG. 3B, when the individual has performed therequested action 365, the computing device 355 may provide anotification to the maintenance system 315 that the requested action 365is complete. The maintenance system 315 may then request additionalelectric vehicle information 370 to determine whether the requestedaction was performed and/or was performed correctly/completely.

Continuing with the tire pressure example from above, when theindividual receives the requested action 365 to add air to one or moretires of the light electric vehicle 335, the individual may indicate,using her computing device 355, that she will perform the requestedaction. Once she has located the light electric vehicle 335 andperformed the requested action, the individual may, using her computingdevice 355, provide a notification to the maintenance system 315, thatthe requested action has been performed. In response to receiving thenotification, the maintenance system 315 may request or otherwisereceive tire pressure information (e.g. additional light electricvehicle information 370) from one or more tire pressure sensors toensure that the requested action was performed as indicated.

As briefly explained above, the system 300 may also be used to match therequesting individual to a particular light electric vehicle 335 based,at least in part, on a determined rider type of the requestingindividual. The rider type may be associated with a particularpredefined rider profile (e.g., an experienced rider profile, a newrider profile, a power rider profile, an aggressive rider profile, acommuter profile, etc.). In some examples, the individual may beinformed of their determined rider type by the light electric vehiclemanagement system 305.

For example, when a reservation request is received by the lightelectric vehicle management system 305, the light electric vehiclemanagement system 305 may inform the individual that she is anaggressive rider. As such, the individual may be matched to a particularsubset of light electric vehicles 335. The rider type may be based onriding habits of the individual (e.g., how fast the individual rideslight electric vehicles 335, how quickly the individual accelerates, howhard the individual applies the brakes of the light electric vehicle335, whether the individual rides/jumps off of curbs, etc.) and/or ariding profile (e.g., routes taken by the individual, the number oftimes the individual has ridden light electric vehicles 335, etc.) ofthe individual and on light electric vehicle information 340. Theidentified rider type may change or be updated by the light electricvehicle management system 305 as additional information (e.g.,additional riding parameter information) is received.

For example, the light electric vehicle management system 305 maydetermine, based on rider profile information 345, that the individualthat submitted the reservation request 350 is an aggressive rider. Assuch, the light electric vehicle management system 305 may identify,using information in the maintenance system 315 and/or route/locationinformation system 320, which light electric vehicles 335 in or aroundthe location of the requesting individual have performance parametersand/or maintenance histories that are best suited to the requestingindividual.

For example, a fleet of light electric vehicles 335 may have differentversions or models of light electric vehicles and some of those modelsor versions may be more suited for aggressive riders than others.Likewise, a fleet of light electric vehicles may have light electricvehicles manufactured by different companies. Once the performanceparameters of the light electric vehicles 335 are identified, the lightelectric vehicle management system 305 may match the individual toparticular light electric vehicle 335 that will be most suited to theindividual's riding style. The location information 360 (FIG. 3B) of theidentified light electric vehicle 335 may be provided to the computingdevice 355 of the requesting individual.

This may include showing, in a user interface of the computing device355, only those light electric vehicles that are best suited to thedetermined rider type of the individual and/or highlighting or colorcoding some or all of the light electric vehicle icons in a userinterface. In some examples, the color coding or highlighting mayrepresent light electric vehicles that are more suitable to thedetermined rider type of the requesting individual. For example, onelight electric vehicle icon on a user interface may be displayed ingreen for a best match while another light electric vehicle icon on theuser interface may be displayed in red to indicate a less desirablematch.

In other examples, the light electric vehicle management system 305 maydetermine a hierarchy of light electric vehicles to show to therequesting individual. The hierarchy may be based, at least in part, onthe rider profile information 345 and the light electric vehicleinformation 340 and/or performance parameters of the light electricvehicles 335. Additionally, the light electric vehicles 335 that aredisplayed on a user interface of the computing device 355 may befiltered based on distance, performance parameters, etc. and may becolor coded or highlighted such as described above.

FIG. 5A-FIG. 5B illustrate an example user interface 500 that displays alocation of light electric vehicles based on matching a determined ridertype of an individual with performance metrics of light electricvehicles. For example, as shown in FIG. 5A, the user interface 500displays a location of the requesting individual (represented by icon540) and the location of three different light electric vehicles(represented by light electric vehicle icon 510, light electric vehicleicon 520, and light electric vehicle icon 530).

However, as shown in FIG. 5B, the light electric vehicle managementsystem may determine, based at least in part on light electric vehicleinformation and on rider profile information that light electric vehiclerepresented by light electric vehicle icon 530, may not be well suited(at least when compared with the light electric vehicles represented bylight electric vehicle icon 510 and light electric vehicle icon 520) tothe rider type of the requesting individual. As such, the location ofthe light electric vehicle represented by light electric vehicle icon530 is not provided on the user interface 500 of FIG. 5B.

FIG. 6 illustrates a method 600 for matching a light electric vehiclewith a requesting individual based, at least in part, on a determinedriding behavior of the requesting individual and one or more performancemetrics of a light electric vehicle. The method 600 may be performed byone or more of the systems shown and described with respect to FIG.2A-FIG. 3B.

Method 600 begins when a light electric vehicle use request is received(610) by a system, such as, for example, a light electric vehiclemanagement system. In some examples, the use request is provided by anapplication executing on a computing device associated with anindividual that wants to reserve and use a light electric vehicle. Theuse request may contain profile information associated with theindividual.

The profile information may include or otherwise be used to determine(620) riding habits (e.g., determine a type of rider) of the individualthat is associated with or that otherwise submitted the light electricvehicle use request. In some examples, the riding habits may be includedor otherwise associated with the light electric vehicle use request. Forexample, profile information received as part of the use request mayinclude information about the riding habits of the individual. In otherexamples, the use request may include information that allows the lightelectric vehicle management system to identify previously received andstored riding habits and/or profile information of the requestingindividual. In yet other examples, riding habits of the individual maybe received by the light electric vehicle management system in real-timeor substantially real-time as the individual is riding the lightelectric vehicle.

Riding habits of the individual may be used to build a rider profile forthe individual. The rider profile may include information about how theindividual likes to ride the light electric vehicle and may includeinformation about how often and when the individual switches gearratios, typical riding speeds of the individual, a pedaling cadence ofthe individual, a pedaling frequency of the individual, an amount ofcharge of a rechargeable battery of the light electric vehicle that isconsumed by light electric vehicle as the individual rides the lightelectric vehicle, how often and when the individual uses an electricassist motor of the light electric vehicle, how aggressively theindividual brakes, how aggressive the individual rides the lightelectric vehicle, etc.

The light electric vehicle management system may also determine (630) alocation of the requesting individual. The location information may bebased on GPS data or other location-based data received from a computingdevice associated with the individual. The location information of theindividual may be included or otherwise associated with the use request.The location information may be used to identify (640) one or more lightelectric vehicles in an area that are associated with the location ofthe individual and that have performance metrics or performancecharacteristics that match the determined rider type of the requestingindividual. The performance metrics of each light electric vehicle maybe based, at least in part, on received light electric vehicleinformation.

For example, if the profile information of the requesting individualindicates the individual typically rides light electric vehicles at aparticular speed, the light electric vehicle management system mayidentify only those light electric vehicles that can travel at thatparticular speed. Once the light electric vehicles are identified, thelocation of the light electric vehicles may be provided (650) on a userinterface of the individual's computing device.

In some examples, the identified light electric vehicles may be filteredand displayed based, at least in part, on how well the performancecharacteristics of the light electric vehicle match the determined ridertype of the requesting individual and/or on how far the light electricvehicle is from the location of the individual. For example, a firstlight electric vehicle may be identified by a green icon or greenhighlight on a user interface of a computing device indicating to therequesting individual that this particular light electric vehicle is agood match for the determined rider type of the individual. However, asecond light electric vehicle may be identified by a yellow or red iconor highlight on a user interface of the computing device indicating tothe requesting individual that the second light electric vehicle is notas good a match for the individual (at least when compared to the firstlight electric vehicle).

In some examples, the matching of requesting individuals to variouslight electric vehicles may be based, at least in part, on a determineddistance between a location of the identified light electric vehiclesand a location of the individual. For example, while the light electricvehicle management system may determine that the first light electricvehicle is a better match for the individual than the second lightelectric vehicle, the second light electric vehicle may be a block awayfrom the requesting individual while the first light electric vehicle isfour blocks away from the requesting individual. As such, the lightelectric vehicle management system may determine that the second lightelectric vehicle is a better match for the requesting individual thanthe first light electric vehicle. As such, the user interface mayrepresent the location of the second light electric vehicle with a greenhighlight or green icon and represent the location of the first lightelectric vehicle with a yellow highlight or yellow icon.

FIG. 7 illustrates a method 700 for detecting a maintenance eventassociated with a light electric vehicle according to an example. Themethod 700 may be performed by one or more of the systems shown anddescribed with respect to FIG. 2A-FIG. 3B.

Method 700 begins when a system, such as, for example, a light electricvehicle management system, receives (710) a light electric vehicle userequest. The request may be received in similar manner to any of thosedescribed herein and may include or be used to identify profileinformation of the requesting individual—including whether theindividual has been trained or is otherwise certified to address one ormore detected maintenance events. When the light electric vehicle userequest is received, the light electric vehicle management systemreceives (720) or otherwise determines information associated with lightelectric vehicles associated with the location of the requestingindividual.

Once the light electric vehicle information is received, the lightelectric vehicle management system may detect (or anticipate) (730) amaintenance event. In some examples, the light electric vehicleinformation may be received in real-time or substantially real-time.Thus, the light electric vehicle management system may also detect amaintenance event in real-time or substantially real-time. If the lightelectric vehicle management system does not detect a maintenance event,the light electric vehicle management system may continue to receive(720) light electric vehicle information such as previously described.

If the light electric vehicle management system detects a maintenanceevent, the light electric vehicle management system may determine (740)an action to address the maintenance event. In some examples, the lightelectric vehicle management system may have access to a database thatstores a list of maintenance events, data indicative of thosemaintenance events and one or more actions that satisfy, solve orotherwise address those maintenance events. In other examples, the lightelectric vehicle management system may provide the light electricvehicle information to a technician and request the technician provideinput (or additional input) regarding one or more possible actions toremedy the maintenance event.

When the action that addresses the maintenance event is determined, theprofile information of the requesting individual is analyzed todetermine (750) a skill set of the requesting individual. For example,the profile information is used to determine whether the requestingindividual has a certification level or has otherwise been trained toperform the action that will address the detected maintenance event.

If the light electric vehicle management system determines theindividual can perform the action, the light electric vehicle managementsystem generates (760) a notification. The notification may include therequested action, one or more instructions regarding how to perform therequested action, a current (or anticipated) location of the lightelectric vehicle and/or an incentive for the requesting individual toperform the action. The notification may be provided to a computingdevice associated with the requesting individual.

The light electric vehicle management system may receive a confirmation,from the computing device of the requesting individual, that therequesting individual will perform the requested action. The lightelectric vehicle management system may also receive (770) confirmationthat the action was performed. In some examples, the confirmation may beprovided by a computing device associated with the requestingindividual. In other examples, one or more sensors associated with thelight electric vehicle may automatically provide information to thelight electric vehicle management system that one or more actions havebeen or are being performed. For example, if the requested action isrelated to tire pressure, a tire pressure sensor may automatically sendupdated tire pressure information to the light electric vehiclemanagement system as the individual is pumping up the tires of the lightelectric vehicle.

When confirmation of the performance of the action has been received,the light electric vehicle management system may request additionallight electric vehicle information from the light electric vehicle inorder to verify (780) the action was performed correctly. Referring backto the tire pressure example, the light electric vehicle managementsystem may determine, using additional tire pressure sensor information,that the requesting individual filled the tires to the requested psi.

FIG. 8 illustrates a method 800 for detecting a maintenance event andidentifying one or more individuals, associated with a current locationor an anticipated destination of the light electric vehicle, that canperform a requested action to address the detected maintenance eventaccording to an example. The method 800 may be performed by one or moreof the systems shown and described with respect to FIG. 2A-FIG. 3B.

Method 800 begins when a system, such as, for example, a light electricvehicle management system, receives (810) or otherwise determines lightelectric vehicle information. This information may be received inreal-time or substantially real-time. In some examples, the lightelectric vehicle information may be received by the light electricvehicle management system as the light electric vehicle is ridden by anindividual.

Once the light electric vehicle information is received, the lightelectric vehicle management system may use the light electric vehicleinformation detect (or anticipate) (820) a maintenance event such aspreviously described. If the light electric vehicle management systemdoes not detect a maintenance event, the light electric vehiclemanagement system may continue to receive (810) light electric vehicleinformation such as previously described.

If the light electric vehicle management system detects a maintenanceevent, the light electric vehicle management system may determine (830)an action to address the maintenance event. When the action thataddresses the maintenance event is determined, the light electricvehicle management system may determine (840) a current location of thelight electric vehicle and/or an anticipated destination of the lightelectric vehicle.

For example, if the light electric vehicle is being ridden by a firstindividual, the light electric vehicle management system may determine,based on route information (stored in profile information associatedwith the first individual), an anticipated destination of the lightelectric vehicle. The anticipated destination (or current location) maythen be used by the light electric vehicle management system identify(850) one or more other individuals that are associated with thelocation and, based on profile information associated with the one ormore other individuals, have training or are otherwise authorized toperform the determined action that addresses the maintenance event.

The light electric vehicle management system may then generate (860) anotification and provide the notification to a computing deviceassociated with the identified one or more other individuals. Thenotification may include the requested action, one or more instructionsregarding how to perform the requested action, a current (oranticipated) location of the light electric vehicle and/or an incentivefor the individual to perform the action.

In some examples, the notification may be provided to a number ofdifferent individuals that are in or are otherwise associated with thedetermined or anticipated location of the light electric vehicle. Insuch examples, the light electric vehicle management system may providethe location of the light electric vehicle to the first individual thatresponds to the generated notification. If the first individual is notable to perform the requested action (either because the individual isnot authorized to perform the requested action, is no longer in or nearthe location of the light electric vehicle and/or cannot perform therequested action within a threshold amount of time) the notification maybe sent to a second individual. In some examples, the actual location ofthe light electric vehicle is not provided to the one or more otherindividuals until the current reservation of the light electric vehiclehas ended (e.g., the first individual ends her use of the light electricvehicle). If the anticipated destination was incorrect, the lightelectric vehicle management system may identify other individualsassociated with an updated anticipated location and/or actual locationof the light electric vehicle.

The light electric vehicle management system may also receiveconfirmation that the action was performed such as previously described.When confirmation of the performance of the action has been received,the light electric vehicle management system may request additionalinformation from the light electric vehicle in order to verify (870) theaction was performed correctly.

FIG. 9 illustrates a method 900 for detecting a maintenance event basedon riding parameters of an individual. In some examples, the method 900may be combined with the other methods described herein to detect amaintenance event. For example, when riding parameters are received thatindicate the presence of a maintenance event (or anticipate amaintenance event) the light electric vehicle management system mayrequest light electric vehicle information to help verify the occurrenceof the maintenance event. The method 900 may be performed by one or moreof the systems shown and described with respect to FIG. 2A-FIG. 3B.

Method 900 begins when rider parameter information is received (910) bythe light electric vehicle management system. For example, the riderparameter information may include current (e.g., real-time orsubstantially real-time) information about a pedaling cadence of theindividual as the individual rides the light electric vehicle, anaverage speed at which the individual is riding the light electricvehicle, the current amount of power of a rechargeable battery used bythe light electric vehicle as the individual is riding the lightelectric vehicle, how often and when the individual shifts gears, and soon.

When this information is received, the light electric vehicle managementsystem compares (920) these riding parameters to a set of previouslyreceived riding parameters. The comparison may be used to detect orotherwise anticipate a maintenance event. For example, using thecomparison, the light electric vehicle management system may determine(930) whether the riding parameters of the individual are below a ridingparameter threshold. In another example, the light electric vehiclemanagement system may determine whether a difference between the currentriding parameter and the previously received riding parameters are abovea difference threshold. In some examples, the riding parameters receivedin operation 910 are compared with other riding parameters from the sameor similar routes taken by the individual.

If the riding parameters are not below the riding parameter threshold(or are above a difference threshold, such as for example a ten percentdifference, a fifteen percent difference, etc.), the light electricvehicle management system may continue to receive (910) ridingparameters of the individual. However, if the riding parameters arebelow a threshold, the light electric vehicle management system mayrequest and/or receive (940) light electric vehicle information from thelight electric vehicle being ridden by the individual.

The light electric vehicle management system may use the received lightelectric vehicle information, either alone or in combination with, theriding parameter information, to detect (950) or otherwise determine amaintenance event and/or determine whether the individual is simplychanging her riding habits. For example, the individual may be ridingslower due to weather, time of the day, or the individual wants to gofor a leisurely ride. In other examples, the riding parameterinformation may be used alone to determine or otherwise detect themaintenance event.

The light electric vehicle management system may then provide (960) amaintenance notification to a computing device associated with theindividual. In some examples, the notification may be provided to theindividual once the maintenance event is detected. In other examples,the notification may be provided to the individual once a use period ofthe light electric vehicle has ended. For example, the notification mayrequest feedback from the individual to determine whether the individualnoticed a difference in performance of the light electric vehicle. Thisinformation may be used to train the light electric vehicle managementsystem to better identify maintenance events and whether somemaintenance events affect the performance of the light electric vehiclewhile others do not affect the performance of the light electricvehicle.

In some examples, the maintenance notification may also be provided tothe light electric vehicle. The maintenance notification may include oneor more instructions that change or alter performance characteristics ormetrics of the light electric vehicle. In some examples, thenotification is accompanied by an audio output, a visual output and/or ahaptic output. For example, if one or more gears are slipping as anindividual changes gear ratios, the light electric vehicle managementsystem may provide instructions to a computing device associated withthe light electric vehicle that prevents an individual from changinggear ratios. In some examples, when remote fixes are applied to thelight electric vehicle in such a manner, a notification of the change inperformance or capabilities of the light electric vehicle is provided toa computing device of the individual and/or directly to the lightelectric vehicle. In the later example, the light electric vehicle mayinclude a display on which the notification may be provided.

Additionally, when such remote fixes are applied, the remote fixes maybe effectively undone or changed when the light electric vehicle isserviced by a technician. In other examples, the remote fix may be apermanent or semi-permanent fix.

FIG. 10 illustrates a method 1000 for detecting a maintenance eventaccording to an example. The method 1000 may be performed by one or moreof the systems shown and described with respect to FIG. 2A-FIG. 3B.

Like method 900, method 1000 begins when rider parameter information isreceived (1010) by the light electric vehicle management system.Although rider parameter information is shown and described herein, themethod 1000 may also be performed when light electric vehicleinformation, either alone, or in combination with, the rider parameterinformation, is received by the light electric vehicle managementsystem.

When this information is received, the light electric vehicle managementsystem compares (1020) the received information to a set of previouslyreceived riding parameters. The comparison may be used to detect (1030)or otherwise anticipate a maintenance event such as previouslydescribed. If the riding parameters are not below a threshold, the lightelectric vehicle management system may continue to receive (1010) ridingparameters of the individual. However, if the riding parameters arebelow a threshold (or above a difference threshold such as previouslydescribed), the light electric vehicle management system may requestand/or receive (1040) additional light electric vehicle information fromthe light electric vehicle ridden by the individual.

The light electric vehicle management system may use the additionallight electric vehicle information, either alone or in combination withthe riding parameter information, to detect or otherwise determine(1050) the cause of the maintenance event. The light electric vehiclemanagement system may then determine (1060) whether the maintenanceevent is addressable by one or more instructions that may be provided toa computing device associated with the light electric vehicle.

For example, the riding parameter information and/or the light electricvehicle information may indicate that an electric assist motor of thelight electric vehicle is not providing enough power for the individualto maintain her desired average speed. As such, the light electricvehicle management system may instruct the computing device of the lightelectric vehicle to cause the electric assist motor to use additionalbattery power to enable the light electric vehicle to reach the desiredspeed.

Referring back to FIG. 10, if the light electric vehicle managementsystem determines the maintenance event is not addressable by aninstruction (e.g., a remote fix such as described above), the lightelectric vehicle is flagged (1070) for maintenance. Once the lightelectric vehicle is flagged for maintenance, the methods (or portions ofthe methods) described in FIG. 7, FIG. 8 and/or FIG. 9 may be performed.

However, if the light electric vehicle management system determines themaintenance event is addressable by an instruction, the light electricvehicle management system provides (1080) the instruction to the lightelectric vehicle.

FIG. 11 is a system diagram of a computing device 1100 according to anexample. The computing device 1100 may be integrated with or associatedwith a light electric vehicle, such as light electric vehicle 235 andlight electric vehicle 335 shown and described with respect to FIG.2A-FIG. 3B. The computing device 1100 may also be associated orotherwise integrated with the various systems shown and described withrespect to FIG. 1-FIG. 3B. As shown in FIG. 11, the physical components(e.g., hardware) of the computing are illustrated and these physicalcomponents may be used to practice the various aspects of the presentdisclosure.

The computing device 1100 may include at least one processing unit 1110and a system memory 1120. The system memory 1120 may include, but is notlimited to, volatile storage (e.g., random access memory), non-volatilestorage (e.g., read-only memory), flash memory, or any combination ofsuch memories. The system memory 1120 may also include an operatingsystem 1130 that control the operation of the computing device 1100 andone or more program modules 1140. The program modules 1140 may beresponsible for gathering or determining rider profile information,light electric vehicle information, riding habit information, and so on.The memory may also store this received/determined information 1150 orotherwise provide access to this information.

The computing device 1100 may also have additional features orfunctionality. For example, the computing device 1100 may includeadditional data storage devices (e.g., removable and/or non-removablestorage devices) such as, for example, magnetic disks, optical disks, ortape. These additional storage devices are labeled as a removablestorage 1160 and a non-removable storage 1170.

A number of different program modules and data files may be stored inthe system memory 1120. While executing on the processing unit 1110, theprogram modules 1140 may perform the various processes described above.

Furthermore, examples of the disclosure may be practiced in anelectrical circuit comprising discrete electronic elements, packaged orintegrated electronic chips containing logic gates, a circuit utilizinga microprocessor, or on a single chip containing electronic elements ormicroprocessors. For example, examples of the disclosure may bepracticed via a system-on-a-chip (SOC) where each or many of thecomponents illustrated in FIG. 11 may be integrated onto a singleintegrated circuit. Such a SOC device may include one or more processingunits, graphics units, communications units, system virtualization unitsand various application functionality all of which are integrated (or“burned”) onto the chip substrate as a single integrated circuit.

When operating via a SOC, the functionality, described herein, may beoperated via application-specific logic integrated with other componentsof the computing device 1100 on the single integrated circuit (chip).The disclosure may also be practiced using other technologies capable ofperforming logical operations such as, for example, AND, OR, and NOT,including but not limited to mechanical, optical, fluidic, and quantumtechnologies. In addition, examples of the disclosure may be practicedusing a computing device associated with or integrated with the electricvehicle and/or in any other circuits or systems.

The computing device 1100 may include one or more communication systems1180 that enable the electric vehicle to communicate with rechargeablebatteries, other computing devices 1195 (e.g., remote computingdevices), a network service and the like. Examples of communicationsystems 1180 include, but are not limited to, radio frequency (RF)transmitter, receiver, and/or transceiver circuitry, a Controller AreaNetwork (CAN) bus, a universal serial bus (USB), parallel, and/or serialports.

The computing device 1100 may also have one or more input devices and/orone or more output devices shown as input/output devices 1185. Theseinput/output devices 1185 may include a keyboard, a sound or voice inputdevice, a touch, force and/or swipe input device, a display, speakers,tactile/haptic output systems etc. The aforementioned devices areexamples and others may be used.

The computing device 1100 may also include one or more sensors 1190. Thesensors 1190 may be used to detect or otherwise provide informationabout the operating condition of the computing device 1100. In otherexamples, the sensors 1190 may provide information about a lightelectric vehicle to which the computing device 1100 is associated. Forexample, the sensors 1190 may include a tire pressure sensor, an imagesensor, a speed sensor, a tire alignment sensor, a rechargeable batterysensor and so on.

The term computer-readable media as used herein may include computerstorage media. Computer storage media may include volatile andnonvolatile, removable and non-removable media implemented in any methodor technology for storage of information, such as computer readableinstructions, data structures, or program modules.

The system memory 1120, the removable storage 1160, and thenon-removable storage 1170 are all computer storage media examples(e.g., memory storage). Computer storage media may include RAM, ROM,electrically erasable read-only memory (EEPROM), flash memory or othermemory technology, CD-ROM, digital versatile disks (DVD) or otheroptical storage, magnetic cassettes, magnetic tape, magnetic diskstorage or other magnetic storage devices, or any other article ofmanufacture which can be used to store information and which can beaccessed by the computing device 1100. Any such computer storage mediamay be part of the computing device 1100. Computer storage media doesnot include a carrier wave or other propagated or modulated data signal.

Communication media may be embodied by computer readable instructions,data structures, program modules, or other data in a modulated datasignal, such as a carrier wave or other transport mechanism, andincludes any information delivery media. The term “modulated datasignal” may describe a signal that has one or more characteristics setor changed in such a manner as to encode information in the signal. Byway of example, and not limitation, communication media may includewired media such as a wired network or direct-wired connection, andwireless media such as acoustic, radio frequency (RF), infrared, andother wireless media.

In view of the above, some examples of the present disclosure describe acomputer-implemented method, comprising: receiving light electricvehicle information from one or more sensors associated with a lightelectric vehicle; determining, using the light electric vehicleinformation, a maintenance event associated with the light electricvehicle; determining, an action that addresses the maintenance event;determining, based at least in part, on profile information of anindividual riding the light electric vehicle, that the individual canperform the action; in response to determining the individual canperform the action, generating a notification that provides informationabout the maintenance event; and sending the notification to a computingdevice associated with the individual user. In some examples, theprofile information includes a certification level of the individual. Insome examples, the certification level comprises one or more actions theindividual is authorized to perform on the light electric vehicle,wherein each of the one or more actions address a particular maintenanceevent. In some examples, an indication is received that the individualhas performed the action. In some examples, the indication is receivedfrom the one or more sensors. In some examples, the indication isreceived from the computing device associated with the individual. Insome examples, the indication includes additional light electric vehicleinformation from the one or more sensors. In some examples, theadditional light electric vehicle information indicates whether theaction was performed correctly.

In some examples, a system comprising at least one processor and amemory coupled to the at least one processor is described. The memorystores instructions that, when executed by the at least one processor,causes the at least one processor to perform operations, comprising:receiving light electric vehicle information from one or more sensorsassociated with a light electric vehicle; determining, using the lightelectric vehicle information, a maintenance event associated with thelight electric vehicle; determining an anticipated destination of thelight electric vehicle based, at least in part, on rider profileinformation associated with an individual that is using the lightelectric vehicle; identifying one or more individuals associated withthe anticipated destination that are qualified to perform an action thataddresses the maintenance event; and sending a notification to acomputing device associated with at least one of the one or moreindividuals, the notification including a request that the at least oneof the one or more individuals perform the action on the light electricvehicle when the light electric vehicle reaches the anticipateddestination. In some examples, the instructions enable updating thedestination based, at least in part, on additional sensor informationreceived from the light electric vehicle; and sending the updateddestination to the computing device associated with the at least one ofthe one or more individuals. In some examples, the destination of thelight electric vehicle is estimated based, at least in part, on profileinformation of the individual that is using the light electric vehicle.In some examples, the instructions enable receiving an indication thatthe at least one individual has performed the action. In some examples,the instructions enable determining, based at least in part, on receivedadditional sensor information, whether the action addressed themaintenance event. In some examples, the instructions enable providing asuggested destination for the light electric vehicle to a computingdevice associated with the individual that is using the light electricvehicle. In some examples, the instructions enable providing thesuggested destination to the computing device associated with the atleast one of the one or more individuals.

In another example, a computer-implemented method is described. Thecomputer-implemented method, comprising: receiving light electricvehicle condition information from a light electric vehicle, the lightelectric vehicle condition information indicating a maintenance event;determining a current location of the light electric vehicle; receivinga riding request from an individual, the individual being associatedwith the current location of the light electric vehicle; determining,based at least in part on profile information associated with theindividual, whether the individual is trained to perform an action toremedy the maintenance event; and when it is determined that theindividual is trained to perform the action to remedy the maintenanceevent, providing a notification to a computing device associated withthe individual, the notification including: the current location of thelight electric vehicle; and the action to be performed on the lightelectric vehicle to remedy the maintenance event. In some examples, thenotification further includes information about an incentive for theindividual to perform the action. In some examples, the method alsocomprises receiving a verification that the individual will perform theaction. In some examples, the method also comprises verifying the actionwas properly performed. In some examples, verifying the action wasproperly performed comprises analyzing additional information todetermine whether the maintenance event is ongoing.

The description and illustration of one or more aspects provided in thisapplication are not intended to limit or restrict the scope of thedisclosure as claimed in any way. The aspects, examples, and detailsprovided in this application are considered sufficient to conveypossession and enable others to make and use the best mode of claimeddisclosure. The claimed disclosure should not be construed as beinglimited to any aspect, example, or detail provided in this application.Regardless of whether shown and described in combination or separately,the various features (both structural and methodological) are intendedto be selectively rearranged, included or omitted to produce anembodiment with a particular set of features. Having been provided withthe description and illustration of the present application, one skilledin the art may envision variations, modifications, and alternate aspectsfalling within the spirit of the broader aspects of the generalinventive concept embodied in this application that do not depart fromthe broader scope of the claimed disclosure.

The invention claimed is:
 1. A computer-implemented method, comprising:receiving light electric vehicle information from one or more sensorsassociated with a light electric vehicle; determining, using the lightelectric vehicle information, a maintenance event associated with thelight electric vehicle; determining, an action that addresses themaintenance event; determining, based at least in part, on profileinformation of an individual riding the light electric vehicle, that theindividual can perform the action; in response to determining theindividual can perform the action, generating a notification thatprovides information about the maintenance event; and sending thenotification to a computing device associated with the individual user.2. The method of claim 1, wherein the profile information includes acertification level of the individual.
 3. The method of claim 2, whereinthe certification level comprises one or more actions the individual isauthorized to perform on the light electric vehicle, wherein each of theone or more actions address a particular maintenance event.
 4. Themethod of claim 1, further comprising receiving an indication that theindividual has performed the action.
 5. The method of claim 4, whereinthe indication is received from the one or more sensors.
 6. The methodof claim 4, wherein the indication is received from the computing deviceassociated with the individual.
 7. The method of claim 4, wherein theindication includes additional light electric vehicle information fromthe one or more sensors.
 8. The method of claim 7, wherein theadditional light electric vehicle information indicates whether theaction was performed correctly.
 9. A system, comprising: at least oneprocessor; and a memory coupled to the at least one processor andstoring instructions that, when executed by the at least one processor,causes the at least one processor to perform operations, comprising:receiving light electric vehicle information from one or more sensorsassociated with a light electric vehicle; determining, using the lightelectric vehicle information, a maintenance event associated with thelight electric vehicle; determining an anticipated destination of thelight electric vehicle based, at least in part, on rider profileinformation associated with an individual that is using the lightelectric vehicle; identifying one or more individuals associated withthe anticipated destination that are qualified to perform an action thataddresses the maintenance event; and sending a notification to acomputing device associated with at least one of the one or moreindividuals, the notification including a request that the at least oneof the one or more individuals perform the action on the light electricvehicle when the light electric vehicle reaches the anticipateddestination.
 10. The system of claim 9, further comprising instructionsfor: updating the destination based, at least in part, on additionalsensor information received from the light electric vehicle; and sendingthe updated destination to the computing device associated with the atleast one of the one or more individuals.
 11. The system of claim 9,wherein the destination of the light electric vehicle is estimatedbased, at least in part, on profile information of the individual thatis using the light electric vehicle.
 12. The system of claim 9, furthercomprising instructions for receiving an indication that the at leastone individual has performed the action.
 13. The system of claim 12,further comprising instructions for determining, based at least in part,on received additional sensor information, whether the action addressedthe maintenance event.
 14. The system of claim 9, further comprisinginstructions for providing a suggested destination for the lightelectric vehicle to a computing device associated with the individualthat is using the light electric vehicle.
 15. The system of claim 14,further comprising instructions for providing the suggested destinationto the computing device associated with the at least one of the one ormore individuals.
 16. A computer-implemented method, comprising:receiving light electric vehicle condition information from a lightelectric vehicle, the light electric vehicle condition informationindicating a maintenance event; determining a current location of thelight electric vehicle; receiving a riding request from an individual,the individual being associated with the current location of the lightelectric vehicle; determining, based at least in part on profileinformation associated with the individual, whether the individual istrained to perform an action to remedy the maintenance event; and inresponse to determining that the individual is trained to perform theaction to remedy the maintenance event, providing a notification to acomputing device associated with the individual, the notificationincluding: the current location of the light electric vehicle; and theaction to be performed on the light electric vehicle to remedy themaintenance event.
 17. The method of claim 16, wherein the notificationfurther includes information about an incentive for the individual toperform the action.
 18. The method of claim 16, further comprisingreceiving a verification that the individual will perform the action.19. The method of claim 16, further comprising verifying the action wasproperly performed.
 20. The method of claim 19, wherein verifying theaction was properly performed comprises analyzing additional informationto determine whether the maintenance event is ongoing.